APPN Set DLUR

The DLUR option extends the support of T2.0 or T2.1 devices containing dependent LUs to APPN nodes. The DLUR function on an APPN network node or an APPN end node works in conjunction with a dependent LU server (DLUS) in a mixed APPN/subarea network. The DLUS function may reside in some other part of the mixed network from the DLUR.

The dependent LU flows (SSCP-PU and SSCP-LU) are encapsulated over an LU 6.2 (CP-SVR) pipe established between the DLUR APPN node and the DLUS SSCP. The CP-SVR pipe is made up of a pair of LU 6.2 sessions using a new CPSVRMGR mode between the DLUR and the DLUS. This pipe brings the SSCP function (in the DLUS) to the DLUR APPN node where it can be made available to attached T2.0/T2.1 nodes containing dependent LUs.

The dependent LU will appear to be located within the domain of the serving SSCP. Session initiation flows will be emulated from the DLUS, but session bind and data paths will be calculated directly between the dependent LU and its session partner. This path may or may not traverse the serving DLUS node.

This option allows you to configure APPN node DLUR parameters.

Answer the following questions:

  1. Enable dependent LU requester (DLUR) on this network node

    This parameter specifies whether a dependent LU requester is to be functionally enabled on this node.

    Valid Values: Yes, No

    Default Value: No

  2. Default fully qualified CP name of primary DLUS (required when DLUR is enabled).

    This parameter specifies the fully qualified control point (CP) name of the dependent LU server (DLUS) that is used by default. The default primary server may be overridden on a link station basis. The default server is used for incoming requests from downstream PUs when a primary DLUS has not been specified for the associated link station.

    Valid Values:

    A string of up to 17 characters in the form of netID.CPname, where:

    Each name must conform to the following rules:

    An existing fully qualified CP name, using the special characters @, $, # from the character set A, continues to be supported; however, these characters should not be used for new CP names.

    Default Value:

    None

  3. Default fully qualified CP name of backup dependent LU server (DLUS)

    This parameter specifies the fully qualified CP name of the dependent LU server (DLUS) that is used as the default backup. A backup is not required, and the null value (representing no entry) indicates the absence of a default backup server. The default backup server may be overridden on a link station basis.

    Valid Values: A string of up to 17 characters in the form of netID.CPname, where:

    Each name must conform to the following rules:

    An existing fully qualified CP name, using the special characters @, $, and # from the character set A, continues to be supported; however, these characters should not be used for new CP names.

    Default Value: Null

  4. Perform retries to restore disrupted pipe

    This parameter specifies whether DLUR will attempt to reestablish the pipe to a DLUS after a pipe failure. If DLUR receives a nondisruptive UNBIND and this parameter is No, DLUR waits indefinitely for a DLUS to reestablish the broken pipe. If the pipe fails for any other reason and this parameter is No, DLUR attempts to reach the primary DLUS once. If this is unsuccessful, DLUR attempts to reach the backup DLUS. If this attempt also fails, DLUR waits indefinitely for a DLUS to reestablish the pipe.

    Valid Values: Yes, No

    Default Value: No

  5. Delay before initiating retries

    This parameter specifies an amount of time for two different cases when the pipe between the DLUR and its DLUS is broken.

    Valid Values: 0 to 2 756 000 seconds

    Default Value: 120 seconds

  6. Perform short retries to restore disrupted pipe

    Valid Values: Yes, No

    Default Value: If Perform retries to restore disrupted pipes is Yes, then the default value is Yes. Otherwise, the default is No.

  7. Short retry timer

    In all cases of pipe failure other than nondisruptive UNBIND, the minimum of Delay before initiating retries and this parameter specifies the amount of time DLUR will wait before attempting to reach the primary DLUS after an attempt to establish this connection has failed.

    Valid Values: 0 to 2 756 000 seconds

    Default Value: 120 seconds

  8. Short retry count

    In all cases of pipe failure other than nondisruptive UNBIND, this parameter specifies the number of times the DLUR will attempt to perform short retries to reach the DLUS after an attempt to establish this connection has failed.

    Valid Values: 0 to 65 535

    Default Value: 5

  9. Perform long retries to restore disrupted pipe

    Valid Values: Yes, No

    Default Value: If Perform retries to restore disrupted pipes is Yes, then the default value is Yes. Otherwise, the default is No

  10. Long retry timer

    This parameter specifies the time DLUR will wait when performing long retries.

    Valid Values: 0 to 2 756 000 seconds

    Default Value: 300 seconds

Select the Submit button.